Previous | Table of Contents | Next |
III-199 If you use SQL Server Anywhere and are connecting your 16-bit client application to either SQL Anywheres 32-bit client or a 32-bit standalone server, you need to make sure that the following registry entries exist. If you are having problems connecting, checking these entries is a good place to start.
Hive: | HKEY_CURRENT_USER |
Key: | Software\ODBC\ODBC.INI\< datasource name > |
Value Name: | AutoStop |
Data Type: | REG_SZ |
Value: | yes |
III-200 | Value Name: | DatabaseName |
Data Type: | REG_SZ | |
Value: | database name |
III-201 | Value Name: | Driver |
Data Type: | REG_SZ | |
Value: | c:\sqlany50\win32\wod50t.dll |
III-202 | Value Name: | PWD |
Data Type: | REG_SZ | |
Value: | SQL |
III-203 | Value Name: | Start |
Data Type: | REG_SZ | |
Value: | c:\sqlany50\win32\dbeng50 |
III-204 | Value Name: | UID |
Data Type: | REG_SZ | |
Value: | DBA |
The 16-bit ODBC Driver Manager (Odbc.dll), provided with SQL Anywhere, lets 16-bit applications access a 32-bit ODBC driver without any changes. However, you must define a datasource with the 32-bit administrator tool. When you create a datasource with the 32-bit ODBC admin tool, entries are created in the registry and in Odbc.ini. Make sure the registry and Odbc.ini are in sync.
Previous | Table of Contents | Next |